ci(NODE-5424): add CI testing for FLE 6.0 with driver latest #3802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is changing?
To prepare for the 6.0 release and the compatabilty matrix between mongodb-client-encryption and the driver, I added a task to our CI that tests the latest driver changes against mongodb-client-encryption@6.0.0. This task runs for all regular CI runs as a part of the custom csfle tests.
I also pulled in the latest alpha of mongodb-client-encryption for all CI runs except the new variant.
To confirm that the new task was running against the correct version of
mongodb-client-encryption
, I added the version of mongodb-client-encryption used (if it's available) to the printout before mocha CI runs. This affects all CI runs but I believe this is a useful improvement. Here is an example: https://parsley.mongodb.com/evergreen/mongo_node_driver_next_rhel80_large_Node20_test_4.4_sharded_cluster_patch_51a573fe99506b81c7ab808898eb9eb63f58f600_64d3af041e2d171079fd9bc0_23_08_09_15_21_41/0/task?bookmarks=0,7369&shareLine=545Is there new documentation needed for these changes?
No.
What is the motivation for this change?
Release Highlight
Fill in title or leave empty for no highlight
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript